Personal injury claim management system

ABSTRACT

A technique for computerized management of a plaintiff&#39;s personal injury case is disclosed. This technique includes establishing records, each reflective of the phase of a corresponding personal injury claim. The first phase corresponds to pre-negotiation of the claim and includes at least a first and second subordinate pre-negotiation stage. Each of these stages includes the generation of a number of prompts directed to obtaining information about the claim. A given record may also be set to a second management phase corresponding to negotiation of the claim or a third management phase representing settlement of the claim. In addition, the present invention discloses a technique to automatic ly generate a demand letter and calculate settlement amounts from information gathered in the record during pursuit of the claim. The management system may also include scheduling various prompts and correspondence with the program in accordance with a predetermined schedule spanning several days.

A computer program listing is included herewith as a microfiche appendixwith a total of 58 fiche sheets and 3,411 frames.

BACKGROUND OF THE INVENTION

The present invention relates to the computerized management of clientdata, and more particularly, but not exclusively relates to themanagement of personal injury claims.

Every year vast numbers of personal injuries occur. The law encouragesinjured parties to seek compensation from those at fault. Typically, theinjured party, the plaintiff, is able to obtain compensation from theparty at fault, the defendant (or the defendant's insurer), bythreatening a lawsuit. In the vast majority of cases, the claim of theinjured party is settled before a trail on the merits results—evenbefore a lawsuit is filed in many cases. By settling legitimate claimsquickly, a more cost-effective conclusion is reached for all partiesinvolved. Moreover, early settlements conserve judicial resources to thebenefit of the public at large.

Unfortunately, efficiently settling these claims ordinarily requires thecoordination and scheduling of doctors, lawyers, insurancerepresentatives, and many others. Generally, the pursuit of a personalinjury claim also requires the injured client's legal representative togather and assimilate large quantities of documents and otherinformation from a variety of sources. Once gathered, this informationis used to negotiate a settlement of a claim or litigate the claim asthe situation warrants. Frequently, poor coordination, scheduling, andinformation management leads to claims that are not settled promptly,properly, or fairly. Sometimes, a poorly managed claim becomes thesubject of costly litigation which otherwise could have been avoided.

In addition, information collection tasks often limit the quantity ofclaims that can be handled at the same time by a given number of legalsupport personnel. The management of information collection required forsome claims often distracts legal representatives from focusing onnegotiation and litigation tasks for other claims. This distractionsignificantly adds to cost and hampers efficiency of the typicalpersonal injury attorney's practice.

Conventional management schemes are often prone to errors due to theimposition of a manual entry in a client's file every time a document issent or other noteworthy event takes place. Moreover, these schemes donot prompt the legal representative or support staff to assure theprompt advancement of the claim from one stage to the next. The untimelyadvancement of a claim through various information gathering andevaluation stages often results in a more expensive and protractedresolution of the claim compared to claims which are investigated,evaluated, and asserted more promptly. Also, conventional schemes oftenmake it difficult to quickly access the status of a given client's casein response to a phone call or other request requiring a quick turnaround.

Consequently, there remains a need for a personal injury managementtechnique to automatically gather, track, schedule, and organize variousaspects of personal injury claims. Preferably, such a system facilitatesa rapid assessment of the status of each claim, and frees legalrepresentatives from tedious and burdensome information managementtasks. Instead, legal representatives may focus on negotiation andlitigation of meritorious claims—increasing the number of claims whichmay be handled simultaneously and improving quality of therepresentation. As compared to conventional schemes, it is preferredthat this management technique facilitate the handling of a largernumber of claims by the same legal support staff with fewer errors.Moreover, the system promotes movement of a number of personal injuryclaims towards settlement in a timely manner. The present inventionmeets these needs and provides other significant advantages.

SUMMARY OF THE INVENTION

The present invention relates to legal claim management. Various aspectsof the invention are novel, non-obvious, and provide various advantages.While the actual nature of the invention covered herein can only bedetermined with reference to the claims appended hereto, certainfeatures which are characteristic of the preferred embodiment disclosedherein can be described briefly.

In one feature of the present invention, a computerized managementtechnique for a plaintiff's personal injury case includes executing aprogram loaded on a computer to establish a client data record. Thisrecord has data relative to a personal injury claim including status ofthe claim. Status of the record is established in a first managementphase which corresponds to pre-negotiation of the claim. The programcharacterizes the first phase with at least a first subordinatepre-negotiation stage and a second subordinate pre-negotiation stage.The program generates a first number of pre-negotiation prompts inresponse to initiation of the first stage. These first prompts aredirected to obtaining information about the claim. The second stage ofthe first phase is activated after completion of medical treatment of aninjury corresponding to the claim. The program generates a second numberof pre-negotiation prompts in response, which are directed to thedetermination of a proposed settlement amount for the claim. The statusof the record is set to a second management phase corresponding tonegotiation of the claim, and a third management phase representingsettlement of the claim. This computerized management system provides aunique organizational structure that facilitates advancement of apersonal injury claim through an optimal sequence of informationgathering stages with a minimum of manual intervention.

In another feature, a computerized management system includesestablishing a number of data records in a computer by executing aprogram. Each of the records corresponds to a different personal injuryclaim which is opened with a first status representing a medicaltreatment phase for a corresponding injury. The program promptsgeneration of a first number of documents in accordance with a firstschedule timed by the program to span a first number of days for each ofthe records. The first documents are correspondingly directed toreceiving information about the claim for each of the records. The firststatus of a selected one of the records is changed to a second status inaccordance with completion of medical treatment for the correspondinginjury. The program prompts generation of a second number of documentsdifferent from the first number of documents in accordance with a secondschedule initiated by the status change. The program times the secondschedule to span a second number of days. The second documents aredirected to formulation of a proposed settlement amount for the injury.The selected one of the records is switched to a third status inresponse to communicating the proposed settlement amount to acorresponding opponent. The selected one of the records is set to afourth status corresponding to litigation of the corresponding claim.The program prompts generation of a third number of documents inaccordance with a third schedule timed by the program during the fourthstatus. Generation of selected ones of the first, second, and thirddocuments may automatically update the corresponding record and triggerone or more prompts to follow-up on whether a response has been receivedto the document triggering the update.

In still another feature of the present invention, a computer system formanaging a number of personal injury cases includes an input device, avideo monitor, and a processor. The processor responds to the inputdevice to generate a number of data records each corresponding to adifferent respective personal injury claim. The processor generates anumber of signals for each of the records, which include a first controlsignal corresponding to pre-negotiation of the respective claim. Thefirst control signal is characterized by at least two subordinatesignals. These subordinate signals include a first subordinate signalcorresponding to medical treatment of an injury associated with therespective claim. The processor is responsive to the first subordinatesignal to time generation of a first number of prompt signals inaccordance with a first schedule spanning several days. Thesesubordinate signals also include a second subordinate signalcorresponding to release from medical treatment for the injury. Theprocessor is responsive to the second subordinate signal to timegeneration of a second number of prompt signals in accordance with asecond schedule spanning several days. The second prompt signals differfrom the first prompt signals. The number of signals generated by theprocessor also include a second control signal corresponding tonegotiation of the respective claim and a third control signalcorresponding to settlement of the respective claim. The monitorresponds to the first prompt signal to display a first number of inputprompts in accordance with the first schedule and to the second promptsignals to display a second number of input prompts in accordance withthe second schedule. The first and second prompts facilitate gatheringand entry of data about the respective claim into a corresponding one ofthe records.

In still another feature of the present invention, a device for acomputer system having a processor, video monitor, and printer isprovided which includes a computer readable medium storing a softwareprogram. The program generates a number of data records eachcorresponding to a different respective personal injury claim. Theprogram places each of the records in a first management phasecorresponding to pre-negotiation of the respective claim. The programcharacterizes the first phase with at least a first subordinate stagecorresponding to medical treatment for an injury associated with therespective claim and a second subordinate stage corresponding tocompletion of medical treatment for the injury. The program displays anumber of prompts on the monitor in accordance with a first schedulespanning a first number of days and generates a second number ofcorresponding documents with the printer during the first stage. Theprogram times display of a second number of prompts on the monitor inaccordance with the second schedule spanning a second number of days andgenerates a second number of corresponding documents with the printerduring the second stage. The program is configured to selectivelyclassify the records in a second management phase corresponding tonegotiation of the respective claim and a third management phasecorresponding to settlement of the respective claim.

In yet another feature, a computerized management technique includesestablishing a number of data records in a computer system forprocessing by a software program executed by the system. The recordseach correspond to one of a number of personal injury claims. The claimseach correspond to a respective client suffering a respective personalinjury. A number of data items are entered into each of the records. Theitems include a factual description of the respective injury, a numberof values corresponding to damages suffered by the respective client,and an address of an opponent to a corresponding claim. One of therecords is selected to generate a demand letter with the system. Theprogram automatically assembles the letter from a standard form, theitems corresponding to the selected record, and a demand amountcalculated by the program from the values corresponding to the selectedone of the records.

In a further feature of the present-invention, a number of data recordsare established in a computer by executing a program, which eachcorrespond to a different personal injury claim. Each record is openedwith a first management phase representing medical treatment for acorresponding injury. A selected one of the records is changed from thefirst phase to a second management phase in accordance with completionof medical treatment for the corresponding injury. This record isswitched to a third management phase in response to communication of theproposed settlement amount to a corresponding opponent. The status ofthe selected one of the records is changed to a fourth management phaserepresenting settlement of the corresponding personal injury for a finalsettlement amount. The program calculates a distribution of the finalsettlement amount among a number of recipients and prompts generation ofa corresponding number of checks with the computer. The selected one ofthe records includes a number of accounting entries. A first one of theentries corresponds to a medical cost for the corresponding injury, anda second one of the entries corresponds to an expense incurred duringthe second or third phases to pursue the corresponding claim. Thedistribution is calculated by the program as a function of the entries.

Accordingly, it is one object of the present invention to provide atechnique for computerized management of personal injury claims.

Another object is to provide a computerized multi-phase managementsystem having subordinate stages for at least one of the phases.

Another object of the present invention is to provide a technique foradvancing a personal injury claim through various information gatheringand evaluation stages to prompt a timely settlement.

A further object is to provide a computerized personal injury claimmanagement technique which facilitates the prompt assessment of thestatus of a claim selected from a large number of claims.

Yet another object is to provide a computerized management system whichgenerates a letter by automatically assembling data from a client recordand calculating relevant quantities for inclusion in the letter.

Another object is to assist legal support staff in the timely andefficient gathering of information from which to formulate a settlementproposal.

A further object is to reduce errors inherent in conventional systemswhich require manual entry of the dates documents are sent.

It is still another object of the present invention to provide acomputerized management technique for generating demand letters andsettlement amounts to facilitate efficient personal injury claimmanagement.

Further objects, advantages, benefits, aspects, and features of thepresent invention will become apparent from the description and drawingscontained herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view of a hardware system.

FIG. 2 is a flow diagram of a personal injury claim process.

FIG. 2A-2D are diagrams graphically depicting selected aspects of a userinterface of a computer program to manage the process depicted in FIG.2.

FIGS. 3A-3D present a flow diagram depicting scheduling routine 200 tomanage selected aspects of stage 114 shown in FIG. 2.

FIGS. 4A-4B present a flow diagram depicting scheduling routine 300 tomanage selected aspects of stage 116 shown in FIG. 2.

FIGS. 5A-5B present a flow diagram depicting scheduling routine 400 tomanage selected aspects of stage 118 shown in FIG. 2.

FIG. 6 presents a flow diagram depicting scheduling routine 500 tomanage selected aspects of stage 130 shown in FIG. 2.

FIGS. 7A-7B present a flow diagram depicting scheduling routine 600 tomanage selected aspects of stage 130 shown in FIG. 2.

FIGS. 8A-8E are flow diagrams illustrating selected prompt schedulingroutines to manage the process depicted in FIG. 2.

FIG. 9 is a diagram depicting a user interface for the computerizeddetermination of settlement disbursements of personal injury claims.

DESCRIPTION OF THE PREFERRED EMBODIMENT

For the purposes of promoting an understanding of the principles of theinvention, reference will now be made to the embodiment illustrated inthe drawings and specific language will be used to describe the same. Itwill nevertheless be understood that no limitation of the scope of theinvention is thereby intended. Any alterations and further modificationsin the described device, and any further applications of the principlesof the invention as described herein are contemplated as would normallyoccur to one skilled in the art to which the invention relates.

FIG. 1 is a schematic view of computerized processing system 20 of oneembodiment of the present invention. System 20 includes processor 30operatively coupled to input devices 40 and output devices 50. Processor30 is configured to perform one or more predetermined routines toprocess information residing in memory 32. In one preferred embodiment,system 20 is configured to execute management program softwarecorresponding to the computer program listing of the MicroficheAppendix.

Processor 30 is also configured to receive portable disk 34 for remotelystoring computer readable information. Input devices 40 include keyboard42 and mouse 44. Devices 40 are used to provide operator input toprocessor 30 as required. Output devices 50 include visual display 52and printer 54. Devices 50 are used to provide output from routinesexecuted by processor 30 in response to input from devices 40. System 20may further include other input or output devices such as a modem,network link, speaker, microphone, or such other devices as would occurto one skilled in the art.

Processor 30 may be a collection of one or more electronic components ora single custom integrated component. Processor 30 may include digitalcircuitry, analog circuitry, or a combination of these circuit types.Although it is preferred that the processor be readily reprogrammable bysoftware, it may also be programmed by firmware, configured as aintegrated state machine, or employ a combination of these techniques.Preferably, processor 30 is configured to digitally receive, process,and output information in a conventional manner; however, it isenvisioned that the present invention may be adapted to other types ofprocessing techniques as would occur to those skilled in the art.

Preferably, memory 32 is of the electronic (e.g. solid state), magnetic,or optical variety which may be readily interfaced with electroniccontrollers or processors. Memory 32 may be integrally associated withsystem 20 or be remotely accessed via a communication link with system20. Disk 34 participates in system 20 as an optionally available memoryaccessible by processor 30. Disk 34 may be a removable optical disk(CD), electromagnetic Hard or floppy disk media, or other portablememory type as would occur to one skilled in the art. Display 52 ispreferably of the color graphic Cathode Ray Tube (CRT) variety.Alternatively, a liquid crystal display or other visual displayresponsive to processor 30 may be used. Printer 54 is preferably of thelaser variety, but could be of another type as would occur to oneskilled in the art.

It is preferred that system 20 be a conventional desktopmicroprocessor-based personal computer system. In one embodiment,processor 30 includes a base unit with a PENTIUM microprocessor suppliedby INTEL corporation configured to operate at a 200 MHz clock speed. Thebase unit also includes memory 32 comprising 32 megabytes (MB) ofconventional semi-conductor Random Access Memory (RAM) components and atleast one conventional electromagnetic hard disk drive unit compatiblewith the microprocessor. Also, it is preferred that the base unitinclude a conventional floppy disk drive configured to receive a 1.44 MBelectromagnetic floppy disk as disk 34. For this embodiment, keyboard 34and mouse 44 are of a conventional variety compatible with the base unitand operatively connected thereto by appropriate cables. Similarly,display 52 is provided by a VGA monitor cabled to the base unit with atleast an 800×600 pixel resolution, and printer 54 is of a compatiblelaser variety cabled to the base unit. System 20 includes all theelectrical and electronic components needed to provide a functional,personal desktop computer for this embodiment. This 200 MHzPENTIUM-based personal computer embodiment of system 20 is preferred forthe execution of the computer program listing of the MicroficheAppendix.

FIG. 2 is a flow chart illustrating personal injury claim process 110.Process 110 begins with stage 112. In stage 112, a client is injured andcontacts an attorney to have their personal injury claim evaluated. Ifthe client decides to retain the attorney and the attorney accepts thecase, control flows to stage 114, otherwise the process terminates (notshown in FIG. 2). Stage 114 includes initiation of a computer clientdata record with a management program executed by system 20, a preferredembodiment of this management program is listed in the MicroficheAppendix. Preferably, the management program supports a large number ofindependently accessible client data records.

Information available at stage 114 is entered into the client's datarecord via one or more of input devices 40. Stage 114 corresponds to atime period during which the client is receiving medical treatment forthe injury. Because the extent and cost of the injury is not yet known,negotiation of the client's claim with the party that caused the injurygenerally does not commence during stage 114. However, informationconcerning the event that caused the injury, such as a slip and fall oran automobile accident, may be gathered. Also, the attorney preferablychecks on the treatment progress of the client and educates the clientas to the personal injury claim process.

Upon release of the client from medical treatment, stage 116 isinitiated. Although some information concerning the scope and nature ofthe personal injury claim is gathered during stages 112 and 114, stage116 focuses on obtaining information specific to establishing a faircompensation amount for the client. For example, medical providerrecords and bills, and information concerning economic loss, such aslost wages, are gathered in stage 116. Once the appropriate informationis gathered, it is presented in a persuasive letter to the person whocaused the injury (the defendant), the defendant's representative, orthe defendant's insurance company. This “demand letter” proposes anamount of compensation needed to settle the client's claim, initiating anegotiation phase of the case. In contrast, stages 112, 114, and 116correspond to a pre-negotiation period of the client's claim. Notably,stage 116 is still a part of pre-negotiation, but is also given the morespecific designation of “Demand in Progress.”

After the demand letter is sent, stage 118 is entered. During stage 118,negotiations between representatives of the client (or plaintiff) anddefendant take place. Frequently, the claim is settled during thisnegotiation period. The prompt and proper execution of stages 114 and116 during pre-negotiation enhance the chances that a settlement will beobtained promptly. However, on occasion, litigation or an AlternativeDispute Resolution (ADR) procedure is initiated. The decision to settleor engage one of the alternative procedures are represented by loop 120.In loop 120, conditional 124 tests whether the claim has been settled.If no settlement has occurred, then conditional 126 is encountered whichtests whether and ADR procedure has been put in place. If there is noADR procedure in place, then control flows to conditional 128 whichtests whether litigation has been initiated. If litigation has not beeninitiated, control flows back to conditional 124 via loop 120 until oneof the series of conditionals 124, 126, 128 is satisfied. The executionof loop 120 may generally be regarded as a occurring simultaneously withthe negotiation phase of the client's claim.

If conditional 124 is satisfied, then control flows to stage 125 tofinalize settlement. Settlement represents a final phase of the client'sclaim. Stage 125 includes receipt of a check in the amount of thesettlement, payment of all parties owed on behalf of the client, and theexecution of settlement papers. Quite often, an attorney representing apersonal injury client pays various expenses incurred in pursuit of theclient's claim out-of-pocket, relying on settlement proceeds to berepaid. Typically, the attorney's fee is paid as a percentage of thecompensation proceeds which result only when the case is settled or afavorable ADR or litigation outcome is obtained. In addition, medicalproviders may be paid from settlement proceeds. Also, another party maybe entitled to a portion of the proceeds by way of subrogation or alien. The accounting and tracking of these payments presents asubstantial challenge which is met by the present invention as describedin connection with FIG. 9 hereinafter.

If conditional 126 of loop 120 is satisfied, then either a mediation orarbitration hearing is conducted in stage 127. Unlike a courtproceeding, ADR procedures are typically privately funded and privatelyconducted. Ordinarily, a statement is filed with the mediator orarbitrator, but the exhaustive discovery and briefings associated withlitigation are usually avoided. Stage 127 assumes termination of theprocess with the ADR procedure; however, in other embodiments,litigation or settlement stages may be encountered after stage 127 (notshown). ADR may be considered a separate phase of the claim oralternatively as a part of the negotiation or litigation phase.

If conditional 128 is satisfied, then litigation stage 130 isencountered. The litigation phase of a claim may include the operationof many concurrent procedures which generally increase the cost ofpursuing the claim. Stage 130 is initiated by filing a formal documentwith the court called a “complaint.” The clerk of the court stamps acopy of the complaint with the filing date and returns it to theattorney who filed it. The parties being sued are formally notified ofthe litigation by service of the complaint. Frequently, an informalnotice is sent via letter by the attorney representing the injuredclient as well. The party or parties being sued formally respond to thecomplaint by filing a document with the court called an “answer” withina specified time period. Usually, this time period may be extended byfiling a motion to enlarge the time required to answer.

Generally, personal injury claimants are required to file a “complaint”within a set time period imposed by a statute of limitations or theirclaim cannot be enforced. This time period is typically measured fromthe date of injury. Thus, when an amount of time has lapsed which isclose to the statute of limitations, it may be necessary to promptlyfile a complaint just to preserve the client's rights. This procedure isnot reflected in FIG. 2.

Another litigation procedure which may be initiated upon filing theComplaint is discovery. Generally, discovery is a process employed by aparty of the lawsuit to obtain information about the case from anotherparty. Typically, informal or “paper” discovery comprises writteninterrogatories, which ordinarily require the opponent to provide awritten response, and requests for production of documents and thingsthat are expected to lead to relevant evidence. In contrast, formaldiscovery includes interrogating witnesses under oath in accordance witha procedure resembling the examination of a witness in court.

This interrogation of a witness through discovery is called a“deposition” which is usually held in the presence of a qualified courtreporter who generates a transcript of the proceeding. A deposition maybe imposed on any party to the lawsuit and on third party witnessesunder certain circumstances. These discovery techniques are typicallyutilized a number of times before trial. Various court rules control thescope of discovery and impose time limits on the time to respond to eachitem. Often, response times for informal discovery may be extended whenthe court grants a motion filed by one of the parties for an enlargementof time to respond.

As trial nears, other litigation procedures tend to dominate. Often,dispositive motions, such as summary judgment motions, are filed. Asummary judgment motion asks the judge to decide an issue of the case asa matter of law; thus eliminating the need to conduct a trial as to thatissue. Sometimes the entire case may be disposed of by summary judgment.A pre-trial conference is usually conducted by the court to make a finalattempt at settlement and establish parameters for trial often includingthe trial date. Prior to trial, the injured client's attorney needs toverify that all required evidence and witnesses are available for trial.Preliminary and final witness and evidence lists are ordinary filed withthe court. Also, “motions in limine” are filed to tentatively preventthe presentation of certain evidence during trial. Finally, the trial isconducted and the outcome reached.

Stage 130 assumes litigation through trial; however, it should beunderstood that many variations are possible. Quite often, settlement isreached during litigation which effectively concludes process 110 withstage 125 (although approval by the court may be additionally required).Similarly, an ADR procedure may be ordered by the court in the midst ofstage 130. Many other variations are also possible.

Having outlined the personal injury claim process, various aspects of asoftware program configured to manage process 110 are next described.The computer program listing of the Microfiche Appendix is oneembodiment of this program. A software program corresponding to thislisting is configured for execution as an application of MicrosoftCorporation's ACCESS 2.0 program. Software corresponding to theMicrofiche Appendix computer program listing is executed by opening“PITS2.MDB” from the ACCESS 2.0 “File” menu. The Microfiche Appendixorganizes the program listing into sections according to type, usingACCESS 2.0 terminology as follows: (1) Database, (2) Tables, (3)Queries, (4) Reports, (5) Macros, (6) Modules, and (7) Forms. PreferablyACCESS 2.0 is operating under a WINDOWS 3.1 user interface environmentwith a compatible Disk Operating System (DOS). Full functionality alsorequires the availability of WORD 6.0 and the existence of the directory“C:\PITS\DOCS” as may be conventionally established under DOS. The WORD6.0, and WINDOWS 3.1 program are also supplied by Microsoft Corporation.In other embodiments, the program listing may be complied to operate asa stand-alone executable file or otherwise modified for execution inanother operating environment using techniques known to those skilled inthe art. In addition, functional features of this program listing may beused separately or otherwise modified as would occur to one skilled inthe art without departing from the spirit of the present invention.

FIGS. 2A-2D illustrate selected user interfaces corresponding to themanagement program of the Microfiche Appendix. FIGS. 2A-2D eachcorrespond to a graphical display generated by the management programand presented on display 52 for perusal by an operator. FIG. 2Aillustrates an introductory display as main menu 101. Menu 101 includesbutton icon 101 a which may be selected to generate Client Info form 150as depicted in FIG. 2B. As used herein, a “button icon” is a graphicalinterface tool that may be selected or “activated” by a point and clickoperation with mouse 44 to correspondingly direct a desired operation ofthe management program.

Referring to FIG. 2B, Client Info form 150 displays selected data fieldsof a client data record. For a given record, one or more data fields mayinclude information previously entered or be blank. Typically, theoccupied data fields vary from record to record. Client records may besequentially displayed and selected using pull-down menus and variousbutton icons as are conventionally employed in the ACCESS 2.0application environment. When a new record is added, the displayed datafields are typically blank and may be filled as required with keyboard42 or mouse 44.

Generally, the management program is configured to support a number ofclient data records which each correspond to a different personal injuryclaim. As used herein, a “record” includes any group of information ordata that may be indexed by one or more data fields or a collection ofdata field sets having one or more data fields in common. Data isentered into the various fields of each record with input devices 40 ofsystem 20 and inserted through various operations of the managementprogram. Operation 151 corresponds to a data field of the client recordwhich is used to choose between open and closed client data records.Closed records correspond to client cases which have been settled orwhich are otherwise no longer active. Open records correspond to claimswhich are currently being pursued. The OPEN or CLOSED radio button iconof form 150 may be selected through a conventional point and clickoperation with mouse 44 to limit the display of client records to thecorresponding type. In FIG. 2B, the OPEN selection is indicated.

Display block 152 corresponds to an attorney identity field whichindicates the attorney assigned to the client's case. Radio button iconsand check box icons may also correspond to data fields of the clientrecord. For example, check box icon 154 a corresponds to a Large claimfield defined by the client record. Box icon 154 a is marked through astandard point and click operation with mouse 44 when the claim resultedfrom a serious injury corresponding to a high compensation amount. Thethreshold for marking this box icon may vary as would occur to oneskilled in the art. Display block 154 b corresponds to a date data fieldwhich indicates when the attorney last called clients with the largeclaim status.

Display block 153 corresponds to a field of the client record containinga client number assigned by a program. Menu block 155 provides apull-down menu of all clients for the selected type by pointing andclicking on block 155 with mouse 44. Preferably, the names of theclients are presented in alphabetical order in a scrollable, pull-downwindow when selected. Rapid movement through the window may befacilitated by typing a portion of the last name of the client beingsought, once this pull-down menu is activated. After a desired name havebeen selected to reside at the top of the list, a point and clickoperation outside menu block 155 switches to the record for the selectedclient.

Display blocks 156 a, 156 b, 156 c correspond to fields having the last,first, and middle name of the selected client, respectively. Displayblocks 157 a, 157 b correspond to client record data fields having thehome and work telephone number of the selected client, respectively.Check box icons 158 a, 158 b correspond to fields indicating theselected client has Uninsured Motorist (UM) and UnderInsured Motorist(UIM) protection. With this kind of protection, it is possible theclient may be able to settle at least a portion of his or her claim fromtheir own insurance company.

Display block 159 corresponds to a coded data field reflecting thestatus of the client's claim. The various status options are describedbriefly in table I as follows: TABLE I Code Description PNPre-Negotiation phase of the client's claim; DIP Demand In Progressphase for the client's claim; N Negotiation phase of the clients claim;L Litigation phase of the client's claim; S Settlement phase of theclient's claim; D Declined representation; and Z Record Closed.

Display block 160 corresponds to a date field of the client recordcontaining the date the client's accident or injury occurred. Displayblock 161 corresponds to a date field containing the date the clientrecord is opened. Display block 162 corresponds to a text field of theclient record in which a textual description of the client's case may beentered.

Button icon 174 is selected to view a client activity log. This log isautomatically generated by the management program for each clientrecord, and may be viewed as a report document and printed with printer54. The management program automatically inserts at least a portion ofthe information contained in this log and inserts information enteredinto the client record throughout the pursuit of the client's claim. Ineffect, this log is structured to provide a hard copy of the informationin the client's record as it existed at the time of selection. This logalso facilitates direct manual entries as discussed hereinafter. Buttonicon 176 is selected to exit form 150.

Data group collection 170 includes an array of data group selectionbutton icons 170 a-170 l. When one of button icons 170 a-170 l isselected, one or more data groups of the client record are listed inwindow 172. These groups may in turn comprise a number of data fieldsorganized as one or more selectable records which are not displayed inform 150 due to space constraints. The data fields and subordinaterecords are typically linked by several common data fields such as theclient name and the client number fields. The operator may branch to aform displaying the data of one of the groups through a mouse point anddouble click operation on the corresponding group name displayed inwindow 172.

When button icon 170 a is selected, window 172 displays the data groupsentitled: (1) Client Information, (2) Client Insurance, (3) Client LogEntry, (4) Subrogation, and (5) Workform. Selecting the ClientInformation group presents another display form, a client personalinformation form, which includes additional information about theclient. This additional information corresponds to fields in the clientdata record which are not displayed in form 150. For example, thisadditional information may include the client's address, gender, socialsecurity number, and date of birth. The client personal information formalso may include the attorney fee arrangement and a text field formiscellaneous notes concerning the client. Also, this form preferablyprovides a check box icon to track whether a medical treatment inventoryletter has been sent to the client. Notably, the management programautomatically marks this check box icon when an operator selects togenerate the letter from the documents preparation routine of themanagement program. Another check box icon is included in the clientpersonal information form to indicate whether a response to the medicalinventory letter has been received. Also, a pull-down menu to select apolice department from which to request a police report in the case ofan automobile accident is provided in the client personal informationform.

The client personal information form includes data fields for key datessuch as the date of the accident, the date the client retains theattorney, and the date of settlement. The client personal informationform presents fields also presented in the form 150 such as the client'sname, case phase, and phone numbers.

If the Client Insurance group is selected, then a corresponding clientinsurance form is presented. This form provides the name, phone, andaddress of the client's insurer and describes selected coverage details.These details may include the amount of medical coverage, and the amountof any Uninsured motorist (UM) or Underinsured Motorist (UIM) coverageavailable. Also, the client insurance form includes a selection field toindicate acknowledgement of representation by the insurance company, andpreferably includes a check box icon to flag whether the insurancecoverage of the client's claim is questionable in some manner.

If the Client Log Entry group is selected, then a client log entry formis presented which allows the operator to manually enter items, notes,and reminders in the client activity log. The manual log entries areeach maintained as a “sub-records” of the client data record. The clientlog entry form permits optional manual entries to be made in addition toentries automatically provided by various operations of the managementprogram.

If the Subrogation group is selected, then a correspondingsubrogation/lien form is displayed. This form displays one or more setsof information which each correspond to a party to which a payment isowed from the client's settlement by way of subrogation or a lien. Theamount owed is also displayed for each of the parties indicated.Preferably, the subrogation/lien entries are indexed by client.

If the Workform group is selected, then a corresponding workform isdisplayed which is arranged to track monetary matters concerningsettlement of the client's claim. One embodiment of this workform isdepicted in FIG. 9 which is described hereinafter.

Button icon 170 b of data group 170 is selected to display a data grouplist in window 172 including: (1) Defendant's Personal Information, (2)Defendant's Insurance Information, (3) Defendant's Independent AdjusterInformation, (4) Defendant's Counsel Information, and (5) Defendant's“Mail To” Information. When the Defendant's Personal Information groupis selected, a corresponding form is generated which displays thedefendant's name and address. The defendant's personal information formalso provides check box icon selections to indicate questionableliability or insurance, and acknowledge whether the defendant isrepresented by an insurer. In addition, date fields are displayed toindicate when a notice of representation letter was sent to either thedefendant or defendant's insurance in accordance with an acknowledgementfield, and when a response was received. A general note field is alsoincluded.

When the Defendant's Insurance Information group is selected, acorresponding form is displayed which presents the defendant's insurer,if any, with address and selected coverage details. When the Defendant'sIndependent Adjuster Information group is selected, a corresponding formis displayed which provides the name and address of the adjuster withother information as appropriate. Selection of the Defendant's CounselInformation group displays a form with the name and address ofdefendant's counsel (if any). Selection of the Defendant's “Mail To”Information indicates the address to which correspondence regarding theclient's claim is to be sent.

When button icon 170 c is selected, the following data groups are listedin window 172: (1) Provider List, (2) Provider Records, and (3) ProviderPayment. When selected, the Provider List group presents a formconfigured to sequentially display each medical provider for the client.The form displays the medical providers name and address, the dates ofmedical treatment, and the nature of the medical treatment fromcorresponding fields of the client record. The Provider List form alsopermits access to a master list of health care providers to assist withentry of a new provider for the client.

Selection of the Provider Records group displays a form that isconfigured to sequentially display the status of medical records,medical treatment narratives, and treatment costs indexed by medicalprovider. The medical records form includes check box icons indicatingwhich records are needed, whether a detailed narrative of theinjury/treatment is needed, and the status of responses to requests forthese items. The management program automatically updates the requeststatus in the client data record when a medical record request is sentwith the program. This update is preferably reflected in the clientactivity log and other selected reports generated by the managementprogram. In addition, this form displays the date request letters weresent and the date of a follow-up phone call.

When the Provider Payment group is selected, a form is generated whichis indexed by medical provider and client. The provider payment form isconfigured to sequentially display the payment status for each providerof the provider list, and includes check box icons to indicate whether acorresponding medical provider bill is needed or has been received.Also, the cost of treatment and the amount paid are indicated asappropriate. A verification check box icon is included to confirm whenpayment has been made.

When button icon 170 d is selected, window 172 displays data groupsrelating to the client's economic loss resulting from the personalinjury. The economic loss groups include: (1) an employer list and (2)employer records. Selection of the Employer List group provides a formto sequentially display the client's employers and correspondingaddresses indexed by client. The Employer Records collection tracksrequests and receipt of records relating to economic loss suffered bythe client. When selected, an employer record form is displayed for eachemployer record entered. The employer record form includes two sets ofdata corresponding to lost wages records and loss of opportunityrecords, respectively. For each set, letter request dates and afollow-up telephone call date are displayed. The letter request fieldsare updated automatically when the management program is used togenerate corresponding request letters. Also, the amount of loss isdisplayed for each set.

Button icon 170 e corresponds to data groups concerning evidence itemsfor the client's case. The evidence groups include: (1) Evidence Listand (2) Witnesses which are displayed in window 172 when button icon 170e is selected. Selection of the Evidence List group displays a formconfigured to sequentially display descriptions of various evidenceitems such as pictures of the injury causing accident, employmentcontracts, pay stubs, and the like. These items are indexed by client.Also, check box icons are provided to indicate request and receiptstatus of the evidence items. A check box icon is also provided toindicate receipt of a police report. Access to a master list of evidencedescriptors may also be obtained from this form via a point and clickbutton. Selection of the Witnesses group displays a form configured tosequentially present the name and address of each witness. In addition,check box icons are provided to indicate whether witness statements andquestionnaires have been requested or received. The request field isentered automatically upon generation of a corresponding request letterwith the management program. A check box icon is also provided toindicate if the witness is needed for trial.

Button icon 170 f corresponds to date driven reminders or “ticklers”generated by a program. Generally, these ticklers are text remindersinserted into appropriate reports and worksheets and selectivelypresented with display 52. Ticklers prompt the operator to take adesignated action on a predetermined date. The Tickler Data groups arepresented in window 172 as: (1) view client daily ticklers and (2)set/view manual tickler items. Throughout the program, several types ofticklers may be employed. One type, an automatic tickler, isautomatically scheduled in response to a designated event or otheraction. Automatic ticklers are often set by delivery of a request letterto prompt an automatic follow-up on the request a predetermined numberof days after delivery. Once the request is satisfied, a correspondingentry is made in the client's record and the automated tickler is markedas completed by the management program so it is no longer generated.Indeed, document generation with the management program may generate asequence of follow-up ticklers which are executed in accordance with apredetermined schedule until a response or other condition is satisfied.These types of ticklers are further discussed in connection with FIGS.3-8.

Another type of tickler is manually set by the operator under theset/view manual ticklers form. Regardless of the origin of the tickler,selection of the view client daily tickler group results in a form thatsequentially displays outstanding ticklers in relation to a specifieddate. The source of the tickler is indicated and a check box icon isalso included which indicates whether the tickler has been completed.The view client daily ticklers form also provides various button iconsto prompt action to satisfy the tickler (a “do it” command) which istypically used to assemble a pertinent letter or document with themanagement program for output with printer 54. Also, button icons areincluded to bring-up the client activity log and view/print various formdocuments.

Selection of the “set/view manual tickler items” data group provides aform to set and display manual ticklers for the selected client record.The data fields specified are the date the tickler is to be activatedand the text reminder to be displayed on the activation date. Alsoprovided is a “view tickler items” button icon which presents a reportthat may be previewed or printed. This tickler report displays theticklers grouped according to whether open or completed. Within eachgroup, the ticklers are listed chronologically.

Selection of button icon 170 g displays “set/view client anchors” inwindow 172. To facilitate the timely and efficient gathering ofinformation for a client's claim, a program is configured to track andgather client record information in accordance with a number ofdate-driven milestones or “anchors.” Each anchor is activated byassociating a start date or “anchor date” therewith. Once activated,each anchor triggers the generation of a sequence of ticklers or otherprompts in accordance with a predefined schedule measured relative tothe anchor date. Each anchor is subordinate to one of the case phasesdescribed in table I. Anchors 1-18 of one embodiment of the presentinvention are described in table II with the relevant case phase asfollows: TABLE II Phase Anchor Description PN 1 Date of Accident PN 2Date Client Retains Attorney DIP (also PN) 3 Client Released FromTreatment N 4 Demand Sent N 5 Date Mediation or Arbitration Hearing SetL 6 Date File Marked Complaint Received L 7 Plaintiff's 1st Set ofDiscovery Documents Sent L 8 Plaintiff's 2d Set of Discovery DocumentsSent L 9 Plaintiff's Third Set of Discovery Documents Sent L 10 DateDeposition Arranged by Plaintiff L 11 Date Deposition Taken/Schedules byPlaintiff L 12 Deposition Taken by Plaintiff L 13 Receipt of Defendant'sDiscovery Documents L 14 Date Deposition of Plaintiff Arranged L 15 DateDeposition of Plaintiff to Take Place L 16 Date Deposition of PlaintiffTaken L 17 Date of Receipt of Trial Date Setting S 18 Case Settled

Activation of “set/view client anchors” in window 172 generates aset/view anchors form which lists anchors that have been set for theclient record and the respective anchor dates. Also, additional anchorsmay be set as required by selecting the appropriate anchor number from apull-down menu and entering the anchor date from this form. Theoperation of anchors and the inter-relation to case phases is furtherdiscussed in connection with FIGS. 3-8. Anchors may also be removed orindicated as complete through activation of button icons provided on theview/set client anchor form. Notably, various forms and processes of themanagement program may automatically remove or set anchors withoutneeding to resort to the set/view anchor form.

Selection of button icon 170 h of client info form 150 displays “send adocument” in window 172. By double clicking on “send a document” withmouse 44, a view/print document form is displayed which provides ascrollable list of various form documents that may be generated with themanagement program. Typically, these documents are customized by themanagement program by inserting designated information from the callingclient record in specified fields of the document. The customizeddocument may be pre-viewed and printed utilizing a merge function withthe WORD 6.0 application. Many of these documents are associated with atleast one data field of the client record and the preparation/deliveryof the document is tracked in the client record. In fact, the clientrecord is typically automatically updated to reflect when the documenthas been prepared. Also, various prompts and ticklers of the managementprogram prompt the automatic assembly and delivery of many of thesedocuments. By way of non-limiting example, a program may provide atickler to generate a letter to request medical records from a medicalprovider.

When the tickler becomes active, this letter is assembled by combiningdata from the client record with a standard form from the document list.Indeed, the management program may set additional ticklers toautomatically follow-up on the request as part of the automated assemblyprocess. When the medical request letter is generated with themanagement program, the program provides for updating the client recordto reflect preparation of the request letter. Updating in this mannerreduces errors compared to conventional systems which require anoperator to manually select and enter data to indicate the delivery ofvarious documents relative to a client record. The view/print documentform is the same form that may be reached by button icon from the “viewclient daily tickler” form.

Selection of button icon 170 i of data group collection 170 displays“negotiation” in window 172. By selecting “negotiation” a negotiationform is presented which includes client record information relating tothe nature of the client's injuries, recovery time, medical treatment,and any scarring that may have resulted from the injury. This form alsopermits data entry regarding negotiation correspondence and otherparticulars via various memo fields. This information is used to supporta formulated negotiation position. If a letter has been sent to theopposing party demanding compensation, this “demand letter” may bequickly pre-viewed by activating a button icon in the negotiation form.This screen is useful to quickly inform the client's attorney about theclient's settlement position when contacted by telephone by the opposingparty. The negotiation form is indexed by client.

Selection of button icon 170 j of data group collection 170 displays“Alternative Dispute Resolution (ADR)” in window 172. By activating thisline, a form is displayed which indicates either an arbitration ormediation ADR type, and the location, date, and time of the ADR hearing(if one has been set). Phone numbers, note fields, and other pertinentinformation may be presented in this ADR form. A check box icon isincluded to indicate if the ADR hearing has already taken place and abutton icon is provided which may be activated to set the hearing date.The ADR form is indexed by client.

Selection of button icon 170 k presents a number of client record datagroups concerning litigation in window 172. These litigation data groupsinclude: (1) Litigation—General, (2) Litigation—Court Information, (3)Informal (paper) Discovery, (4) Depositions—Schedule, (5)Depositions—Records, (6) Non-party, (7) Trial, and (8) Litigation—Notes.Selection of “Litigation—General” displays a form that tracks variousdates associated with litigation.

The Litigation—General form is indexed by client and includes a checkbox icon to indicate if an answer to a served complaint or a motion forenlargement of time has been received, and if so the date of receipt isincluded in a date field. This form also displays a date fieldcorresponding to the date the complaint was filed and the date thecomplaint was marked filed. A check box icon field corresponding towhether the marked complaint has been received is also included, as is adate field showing the date the marked complaint was received from thecourt. This form further includes fields corresponding to the name andcounty of the court having jurisdiction over the matter. Also, datafields corresponding to the filing of Summary judgment motions by eitherparty are included. The Litigation—General form includes data indicatingwhether summary judgment motions have been filed and the time and dateof any hearing scheduled concerning such motions. This form alsoincludes fields to indicate the time and date of a pre-trial conference.The time and date of trial is also displayed in this form. In addition,date fields corresponding to documents filed to request a trial date areincluded. Notably, the dates the requesting documents were prepared withthe program are also recorded automatically in these date fields.

Selection of “Litigation—Court Information” generates a correspondingform that has data fields for the court name, address, judge, causenumber, and defendant names. Selection of “Informal Discovery” generatesa corresponding form that highlights information regarding various paperdiscovery items. The informal discovery form has fields reflectingwhether informal discovery interrogatories or requests that have beenfiled and which party filed them. Also, dues dates, and any enlargementof time motions which have been granted are reflected in appropriatedata fields in this form. This form is indexed by client and includesbutton icons to add and delete discovery items as needed.

Selection of the “Depositions—Schedule” group from window 172 generatesa corresponding form which has data fields for the person being deposed(deponent), the address of the deponent, the location of the deposition,the court reporter hired to attend and prepare the transcript, and thetime and date of the deposition. The court reporter data may be selectedfrom a master list provided as a pull-down menu in this form. A checkbox icon indicating if the deposition was held is also provided. Thedepositions—schedule form is indexed by client.

Selection of the “Depositions—Records” group from window 172 generates acorresponding form which has data fields corresponding to the trackingof the transcript resulting from a deposition. When a client is deposed,the client is given and opportunity to review the transcript first andmake corrections. Check box icons are provided in thedepositions—records form to track receipt and review of an originaltranscripts by the client. Also, a check box icon is provided toindicate if a copy of the transcript has been received for alldepositions that have taken place. This form also includes data fieldsto identify the person deposed, the deposition time/date/place, thereporter name, and text fields for the optional entry of notes.

Selection of the “Non-Party” group from window 172 generates acorresponding form which has data fields directed to the name, address,representation (if any), and telephone number of any third parties otherthan the client (plaintiff) and defendant. Selection of the “Trial”group from window 172 generates a trial form that tracks whether varioustrial pleading have been received and whether various documents havebeen filed with the court. This form also includes the pre-trialconference and summary judgment data fields presented in theLitigation—General form. Pleadings tracked by this form includedespositive motions, preliminary and final witness and exhibit lists,proposed jury instructions, and motions in limine. Selection of the“Litigation—Notes” group from window 172 results in the presentation ofa form with data fields showing the court name and county, the pre-trialconference information, and the summary judgment information previouslydiscussed. This form also includes textual note fields and litigationdocument distribution description fields. Generally, all data groupsselectable from window 172 in response to activation of button icon 172k are indexed by client.

Activation of button icon 1701 displays “Check Information” in window172, which, when selected, generates a form that highlights informationabout checks generated on behalf of the client. Typically, these checksare used to pay for expenses, costs, and fees incurred during thepursuit of the client's claim.

The forms displayed in response to selection of a data group listed inwindow 172 typically each include a number of common button iconoptions. These options include: (1) demand wizard, (2) defendant lookup,(3) the client log, and (4) an exit button. The demand wizard buttonicon is selected to generate a demand letter. Demand letter generationwith the management program is further discussed in connection withscheduling routines 300 and 400 hereinafter. The defendant lookup buttonicon facilitates finding a record based on the defendant's name. Theclient log button icon accesses the client log previously discussed. Theexit button icon returns to form 150 from the currently active form.

Generally, data groups 170 of form 150 provide access to a comprehensivecollection of data for each client record which enables the efficienttracking of all stages of the client's claim. However, the day-to-daymanagement of multiple client records is enhanced by the ability tocollate actions needed to be taken on behalf of multiple clients on adaily basis.

Referring back to FIG. 2A, button icon 101 b is activated to select theDaily Tasks menu 181 as illustrated in FIG. 2C. Menu 181 is arranged tofacilitate the prompt and efficient updating of a number of clientrecords. Menu 181 includes button icon 181 a which is activated tomanually enter activities in a calendar table maintained by themanagement program. Menu 181 also includes button icon 181 b which isactivated to generate the daily tickler form previously discussed as anoption in window 172 when button icon 170 f of Client Info form 150 isactivated. Selection of button icon 181 c of menu 181 generates a dailyworksheet which lists outstanding ticklers and other prompts, indicatingactions that need to be taken to maintain advancement of all open clientcases relative to a specified date. The scheduled generation of theseticklers and prompts to provide for the timely and efficient advancementof a client's claim from one phase to the next is further described inconnection with FIGS. 3-8. The worksheet presents the clients inalphabetical order with the outstanding action items being indicatedadjacent to the client name. When multiple action items exist, then theitems are chronologically listed by the date action should be taken.This worksheet is typically printed using printer 54 to facilitatehandling by the legal support staff of the attorney's officerepresenting the client.

Button icon 181 d is selected to generate a form that sequentiallypresents selected aspects of the client records in the negotiationphase. This dedicated negotiation form focuses attention of the legalsupport staff on this critical phase of the personal injury claimprocess. Exit button icon 181 e is selected to return to main menu 101from menu 181.

Main Menu 101 of FIG. 2A also includes button icon 101 c which isselected to bring-up Reports Menu 182 depicted in FIG. 2D. Menu 182provides for the selection of various reports organized by report group.Group 183 focuses on client data and includes button icon 183 a togenerate a report that alphabetically lists all open client records inaccordance with case phase status. Group 183 also includes button icon183 b to select a comprehensive client log which includes the clientactivity log for every open client record alphabetically. Button icon183 c is included in group 183 to generate a report summarizing onlythose open client records having a large claim status. Group 183 alsoincludes button icon 183 d to generate a report summarizing selectedaspects of settled cases.

Menu 182 also includes report group 184 which is directed to variousscheduled meetings that require the attendance of the client's attorney.Group 184 includes button icon 184 a which provides a reportsummarizing, in alphabetical order, selected aspects of client recordswith scheduled ADR hearings. Button icon 184 b of group 184 is selectedto provide a report of schedule depositions in alphabetical order by thename of the person who is the subject of the discovery. Button icon 184c of group 184 is selected to generate a Trial/ADR calendar from aselected date forward in chronological order.

Menu 182 includes report group 185. Group 185 has button icon 185 a togenerate a weekly calendar of scheduled events requiring attorney actionfor a one week period including a selected date. Group 185 also hasbutton icon 185 b to generate a monthly calendar in the same manner.

Group 186 of menu 182 provides reports directed to critical phases ofclient's claims. Button icon 186 a of group 186 is selected to generatea report in alphabetical order of all clients in the Demand In Progress(DIP) phase. Prompt gathering of relevant information after a client isreleased from treatment is essential to the efficient advancement of acase from the pre-negotiation phase to the negotiation phase ashighlighted by the report of button icon 186 a. Button icon 186 b ofgroup 186 is selected to generate a report in alphabetical order of allclients in the negotiation phase to facilitate prompt and fairsettlement.

Group 187 provides reports directed to claims which may be in jeopardy.Button icon 187 a of group 187 is selected to provide an alphabeticalreport by client name of all claims where the insurance coverage isquestionable. Button icon 187 b of group 187 is selected to generate analphabetical report by client name of all claims where the defendant'sliability may be questionable. Button icon 187 c of group 187 isselected to provide an alphabetical listing of claims where the statuteof limitations is close to running out or may otherwise be an issue.

Group 188 provides reports relating to discovery. Button icon 188 a isselected to provide a report summarizing discovery items by thedefendant in alphabetical order by the client's name. When multiplediscovery entries exist for the same client, the entries are inchronological order. Button icon 188 b is selected to provide a reportsummarizing discovery items by the plaintiff in alphabetical order bythe client's name. When multiple discovery entries exist for the sameclient, the entries are in chronological order. Exit button icon 189 isselected to return to main menu 101.

Menu 101 also includes button icon 110 d which is activated to view datarecords that track the referral source of clients. The referral sourcesinclude various television programs, telephone yellow pages, and medicalprovider referrals. Button icons are provided to view master television,yellow page, and medical provider referral tables; and to generate areport that summarizes referrals by source type for a given date range.Menu 101 has button icon 101 e which is activated to access variouscheck writing and accounting functions provided by the managementprogram. Menu 101 also has button icon 101 f to present a systeminformation menu concerning selected aspects of the program such asmaster tables of attorneys, documents, evidence items, court reporters,medical providers, and trial items. The system information menu alsoprovides information relative to ticklers and anchors which arediscussed further in connection with FIGS. 3-8.

Returning to FIG. 2, during process 110, the management programschedules a number of prompts (including selected ticklers) in variousstages relative to an active anchor date. The prompts are presented toan operator of the management program such as the client's attorney orlegal support personnel via one or more of output devices 50. Themanagement program is configured to maintain anchor schedules for eachclient record independent of the others. Notably, the various anchorsmay be initiated on different dates for different client records,requiring the management program to independently maintain the anchorschedules for each client record. For each anchor, the managementprogram generally executes as series of related prompts that aregenerally directed to promoting various actions to advance each client'sclaim through pre-negotiation, negotiation, and on to settlement.Typically, the operator responds to these prompts by providing an inputwith one or more of input devices 40 or takes such other action asdirected. Generally, once an entry is made in a client's record thatsatisfies a given prompt, follow-up prompts related to the data entryare considered completed and further presentation is accordinglysuppressed. Once all prompts for a given anchor are completed, theanchor is considered complete.

If prompted to send a letter to a party, the management program istypically configured to offer the operator the option of generating theletter with the program by merging appropriate information from theclient record with a form letter from the documents table. The lettermay be printed with printer 54. Furthermore, the management programtypically updates appropriate fields in the client data record which mayinitiate further prompts or ticklers to advance the client's case. Asresponses to letters and other prompted actions are received, theinformation is entered into the client's record as appropriate.Generally, status of the client records advance as the various promptsare addressed. A case phase change for a given client record typicallycorresponds to the initiation of a corresponding anchor via themanagement program.

Process 110 begins with stage 112. In stage 112 anchors 1 and 2 areconcurrently activated. For anchor 1, the anchor date is the date of theaccident. Anchor 1 is directed to assuring that the complaint is filedbefore expiration of the statute of limitations time period.Specifically, in response to setting anchor 1, the management programprompts a review of the client's file for non-parties that should beadded to the complaint as defendants and prompts creation of a complaint(if none was previously filed) or prompts amendment of a previouslyfiled complaint 510 days after the date of accident. This 510 day timeperiod is selected in accordance with the applicable statute oflimitation which may differ with the pertinent legal jurisdiction. Asecond prompt is provided 20 days later (530 days after the complaint)prompting inquiry into whether the complaint or amended complaint with afiling stamp of the clerk of the court has been received by theattorney. If not, the operator is prompted to telephone the court orre-file the complaint.

Anchor 2 has an anchor date of the day the attorney is retained by theclient. Scheduling routine 200 of FIGS. 3A-3D further details theoperation of anchor 2. Routine 200 starts when the anchor 2 date isentered, triggering a number of prompts in accordance with a schedulespanning several days. The management program is configured toindependently execute routine 200 for each client record when anchor 2and the corresponding anchor 2 date are set for a client record.

Referring to FIG. 3A, operation 202 of routine 200 presents a prompt togenerate a letter to the client indicating that the attorney has beenretained by the client. Next, conditional 204 is encountered which testswhether the defendant to the client's injury is represented byinsurance. If so, then the operator is prompted to send a notice ofrepresentation to the defendant's insurer in operation 206. If thedefendant does not have an applicable insurance carrier, then theoperator is prompted to send a notice of representation directly to thedefendant in operation 208. At conditional 210, the operator is promptedto determine whether there are any witnesses to the incident resultingin the client's injury. If so, then in operation 212, the operator isprompted to generate and forward a witness questionnaire letter to eachwitness. The questionnaire letter may be generated at the operator'sdiscretion.

The program then times the lapse of 5 days from the anchor 2 date inblock 214. Once this period has lapsed the program prompts whether theinjury resulted from an automobile accident via conditional 216. If so,the program prompts the request of a police report in operation 218. Theprogram awaits the passage of a total of 10 days from the anchor 2 datein operation 220 and prompts the preparation of an explanatory letterfor the client.

Next the program waits a total of 15 days from the anchor 2 date inaccordance with block 221. Referring to FIG. 3B, conditional 222 isexecuted at the 15 day mark. Conditional 222 prompts an inquiry intowhether evidence has been received from the client. If not, the operatoris prompted to generate and send an appropriate request letter to theclient in operation 224. The program then waits for 20 days to lapsefrom the anchor 2 date in operation 226. At the 20 day point, operation226 prompts generation of a letter reminding the client to continuetreatment as appropriate. Operation 226 also prompts the attorney tocall the client to review the case. Control flows to conditional 228 todetermine whether a requested police report has yet been received inresponse to operation 218. If not, a second request is prompted inoperation 230.

Control then flows to operation 232 where the program times a total of30 days from the anchor 2 date. At the 30 day mark, operation 232prompts generation of a letter to the client inquiring into the physicalcondition of the client and to determine if the client has changedmedical providers. Conditional 234 follows, which prompts thedetermination of whether the attorney's representation has beenacknowledged by the party receiving the notice in either operation 206or operation 208. If not, then conditional 236 determines if there is aninsurer for the defendant. If the defendant does not have insurance,then a second letter to the defendant is prompted in operation 238. Ifthe defendant is insured, then a second letter to the insurancerepresentative is prompted in operation 240. Control flows toconditional 242 from operations 238, 240 which again prompts todetermine whether evidence has been received from the client. Ifevidence has not been received, then another evidence request letter isprompted in operation 244. It should be understood that such additionalrequest letters are automatically customized to list only those evidenceitems that have not yet been marked as received from the client in thecorresponding client record.

Referring to FIG. 3C, conditional 246 is next encountered, which againprompts whether the witness questionnaire has yet been received. If thequestionnaire has not been received, then operation 248 prompts thegeneration of a second questionnaire request letter. Operation 250 isnext encountered, which waits until 45 days lapse from the anchor 2 datebefore taking action. Once the 45 day period has lapsed, operation 250prompts a letter to the client reminding the client to continue medicaltreatment. Also, a conditional to determine acknowledgement ofrepresentation is again encountered in conditional 252. If there is notacknowledgement, then conditional 254 tests whether the defendant isinsured. If not insured or otherwise represented, another letter to thedefendant is prompted in operation 256. If the defendant is insured,then operation 258 prompts generation of another letter to therepresentative.

Operation 260 is next encountered which times the lapse of 60 days fromthe anchor 2 date, then prompts a letter to the client inquiring intothe client's medical condition and whether any change in medicalproviders has occurred. Referring to FIG. 3D, conditional 262 is thenencountered which prompts to determine whether representation has yetbeen acknowledged. If there has been no acknowledgement still, thenconditional 264 tests whether the defendant is insured or has otherrepresentation. If the defendant is not represented, then the attorneyis prompted to telephone the defendant in operation 266. If thedefendant is represented, then the attorney is prompted to call therepresentative in operation 268.

Operation 270 is next encountered which waits until 90 days lapse fromthe anchor 2 date, then prompts the attorney to telephone the client toreview the case. In operation 272, after 120 days have lapsed, theprogram prompts the generation of a letter to the client to inquire intothe client's physical condition and whether there has been a change ofmedical providers. After 135 days from the anchor 2 date, operation 274prompts the attorney to telephone the client to discuss the case. Inoperation 276, a letter to the client is prompted inquiring into theclient's medical condition and medical provider status. At intervals of240, 300, and 360 days from the anchor 2 date, the attorney is promptedto call the client in operations 278, 280, 282, respectively. Operationsfor routine 200 are then completed.

Anchor 3 is initiated with the release of the client from medicaltreatment, and is set to the client's medical release date,corresponding to stage 116 of process 110 (see FIG. 2). Schedulingroutine 300 of FIGS. 4A and 4B details the operation of anchor 3.Routine 300 begins with operation 302 which prompts generation of aletter to the client for an inventory of the client's medical treatmentduring anchor 2. A request for a copy of medical records of knownmedical providers is also prompted in operation 302. Conditional 304 isnext encountered which prompts the determination of whether the clientmissed work as a result of the injury. If work was missed, thenoperation 306 prompts a request to the client's employer for a statementof the client's lost wages. Control flows to conditional 308 which testswhether the client's injury was of a serious nature. If the injury wasserious, then a narrative from one or more medical providers is promptedin operation 310.

Next, the program times an interval of 10 days from the anchor 3 date(medical treatment release date) in block 312. Conditional 314 isencountered at the 10 day point which prompts whether the medicalinventory letter prompted in operation 302 has been received. If theinventory letter has been received, then a request of a copy of medicalrecords from previously unknown medical providers is prompted inoperation 316. In operation 318, the attorney is prompted to telephonethe client and meet with the client as required. The program then timesthe lapse of 20 days from the anchor 3 date in block 320.

Referring to FIG. 4B, conditional 322 is encountered at the 20 daypoint. Conditional 322 prompts to determine whether medical records haveyet been received. If the medical records have not been received, thenoperation 324 prompts a second request letter to the medical providerswho have not responded. Conditional 326 is also encountered at the 20day point to follow-up on the lost wages statement requested inoperation 306. Control then flows to block 330 where the program times atotal lapse of 30 days from the anchor 3 date. Conditional 332 is nextencountered which prompts the determination of whether the medicalrecords requested in operations 302, 316, 324 have yet been received.For records not yet received, a request is prompted in operation 334.Conditional 336 inquires again into whether the lost wages statement hasyet been received from the employer as requested in operations 306, 328.If not received, another request for the lost wages statement isprompted in operation 338. The operations of routine 300 and anchor 3are then complete.

Anchor 4 is initiated by sending a demand letter to the defendant or thedefendant's representative, corresponding to stage 118 of process 110(see FIG. 2). The satisfaction of prompts and information targeted forcollection under anchors 2 and 3 generates a prompt to initiatepreparation of a demand letter by the operator. The program assemblesthis letter from information entered by the operator in response toprompts of anchors 2 and 3 through the execution of routines 200 and300. The program further assembles the letter from a standard form andparagraphs that are selected or customized by the operator through ademand letter wizard operation. Also, the program also automaticallyperforms calculations to account for all expenses, costs, and otherdamages in formulating a proposed compensation amount for inclusion inthe demand letter.

Once demand letter preparation is selected, the demand wizard provides aselectable sequence of displays to assemble the letter. The programbegins with an explanatory form, then advances to present a standardintroductory paragraph in another form which may be altered as required.In the next form, a paragraph may be composed to relay personal detailsconcerning the client which are deemed to be persuasive in achieving thedesired settlement amount. A custom paragraph details facts concerningthe accident that caused the injury is next prompted by a correspondingform. A paragraph directed to the applicable law is next composed orselected from a pull-down menu of form paragraphs. Next, a paragraphdetailing the client's course of treatment is authored. A treatment costreconciliation form is then presented which directs the operator toverify medical provider bills before medical costs will be calculatedfor inclusion in the demand letter. A default paragraph regardingintangible damages is next presented by form that may be altered asneeds require. Next, a paragraph summarizing the client's loss ofearnings is prompted by form. The program calculates and inserts amountscorresponding to lost wages and loss of opportunity resulting from theinjury as previously gathered during anchors 2 and 3. A standardparagraph directed to lost wages law is then provided by form which maybe altered as required. The next form presented prompts the operator toselect from among several other types of damages not yet quantitized,including: (1) pain and suffering, (2) loss of enjoyment of life, (3)permanent impairment, (4) mental anguish, (5) travel to/from medicaltreatment, and (6) loss of spousal services. The operator is prompted toassign compensation amounts to the selected damage types added from thislist. The operator is then prompted to preview or print the letter withthe automatically calculated total proposed settlement amount.

Once the demand letter is prepared, the operator is prompted to setanchor 4 which moves the case to the negotiation phase and automaticallysets appropriate prompts associated with negotiation of the claim.Scheduling routine 400 details the operation of anchor 4 as illustratedin FIGS. 5A-5B. Referring to FIG. 5A, an interval of 15 days from thesending of the demand lapses in block 402. At this 15 day point,conditional 404 is encountered to determine whether a response from thedefendant or defendant's agent has been received. If no response hasbeen received, then operation 406 prompts generation of a letterinquiring into whether to expect a counter-offer to the demand. Controlflows to operation 408 which times a total of 30 days from the anchor 4date, then prompts delivery of a letter to the defendant or defendant'srepresentative to propose an Alternative Dispute Resolution (ADR)process (such as arbitration or mediation) if no response to the demandhas been received. Block 410 represents the lapse of 55 days from theanchor 4 date. At the 55 day point, conditional 412 is executed whichtests whether a response to the ADR letter prompted by operation 408 hasbeen received. If no ADR response has been received, then the attorneyis prompted to call the defendant's representative in operation 414. Alapse of 80 days from the anchor 4 date is timed in block 416. At this80 day point, a determination of whether an ADR date has been set isprovided by conditional 418. If no date has been set, then thepreparation and filing of a complaint to initiate a lawsuit on behalf ofthe client is prompted in operation 420. Copies of the complaint areforwarded to the client and defendant's representative in operation 420as well. On the other hand, if an ADR date has been set, then thecomplaint filing is delayed in operation 422.

Referring to FIG. 5B, a lapse of 90 days from the demand date is timedin block 424. At this 90 day point, conditional 426 prompts to determineif a copy of a complaint, previously filed with the court on behalf ofthe client, has been returned with the filing date stamp. Conditional426 verifies that the lawsuit process has been initiated. If the markedcopy of the complaint has not been received, then operation 428 promptsfollow-up action with the court in a few days. Conditional 430 is nextencountered which checks whether an ADR hearing was held after a totallapse of 100 days from the anchor 4 date. If an ADR hearing was notheld, then a complaint is prepared and filed, with copies to appropriateparties via operation 432. Also at the 90 day point, conditional 434prompts to determine if a marked complaint, previously filed, has beenreceived after the lapse of a total of 110 days from the anchor 5 date.If the marked complaint has not been received, then a follow-up in a fewdays is prompted by operation 436. The operations of routine 400 andanchor 4 are then completed.

Returning to FIG. 2, conditional 124 of loop 120 is encountered.Conditional 124 test whether settlement has been reached. If settlementhas been reached, then control flows to stage 125 to finalizesettlement. When the case is settled, the management program sets anchor18 with the settlement date and a corresponding schedule of prompts areprovided. These prompts include prompting an operator to determinewhether settlement documents have been received ten days after theanchor 18 date. If the documents have not been received, a telephonecall to the defendant's representative is prompted. If the settlementdocuments have been received, then a telephone call to the client isprompted. Next, the program times a lapse of 30 days from the anchor 18date and then prompts to determine if settlement pleadings have beenreceived. If the settlement pleading have not been received within 30days, a call to the defendant's representative is prompted, otherwise aprompt to close and purge the client's file is generated. The settlementprocess ordinarily concludes with the delivery of a check in an amountagreed upon in reaching the settlement. This check is deposited andvarious client expenses, costs, and fees are then paid from thesettlement proceeds.

Another feature of the present invention is the computerized accountingand disbursement of payments to various parties from the settlementproceeds. One embodiment of this technique is described in connectionwith the diagrammatic representation of workform 801 shown in FIG. 9.Workfrom 801 may be displayed in response to the selection of theWorkfrom data group displayed in window 172 when button icon 170 a ofclient info form 150 is activated (see FIG. 2B and accompanyingdiscussion). Workform 801 includes client data area 802 which displaysselected data fields from the client's data record, such as the client'sname, client number, and telephone numbers. Also, it is preferred thatdata area 802 display case phase and indicate whether the client's claimincludes uninsured or underinsured motorist coverage. The remainder ofthe data presented or entered in workform 801 is indexed by client.

Workform 801 has various viewing options which are activated by buttonicons 804 a-804 e. Window 810 displays various sets of data in responseto activation of a corresponding button icon. Also, display block 806indicates the contingent fee percentage charged by the attorney, anddisplay block 808 indicates the corresponding dollar amount of theattorney's fee. The data fields of workform 801 are part of the clientdata record, being generally indexed by client.

When button icon 804 a of workform 801 is activated, window 810sequentially displays information pertaining to each defendant fromwhich settlement is sought. This information includes the defendant'sname and “mail to” destination. A data field for the settlement amountis included for each defendant with corresponding check box icons toseparately indicate the receipt and deposit of a respective settlementcheck. It should be understood that this information is part of theclient's data record and is typically entered earlier in other forms ofthe management program and collected in the workform to facilitate thesettlement procedure.

Selection of button icon 804 b displays information concerning expensespaid by the attorney on behalf of the client in window 810. Window 810sequentially displays each expense item, including a description of theexpense item, the party paid, and the amount paid. The information foreach item also includes a check box icon to indicate whether a check wasprinted with the program, and a check box icon to indicate whether toinclude the expense in the settlement calculation.

Selection of button icon 804 c displays medical provider information inwindow 810. A set of information for each provider is sequentiallydisplayed. This information set includes data fields corresponding tothe identity of the provider, the provider phone number, the treatmentcost and the amount of this cost to include in the settlementcalculation. For each provider information set, a check box icon isincluded to verify the amount to include in settlement. The set alsoincludes a check box icon to indicate whether to include the provideritem in a itemized settlement breakdown that is forwarded as part of aletter to the client. Each provider set has a further check box icon toindicate whether a check needs to be written to the medical providerfrom the settlement proceeds.

Selection of button icon 804 d displays subrogation/lien information inwindow 810. A set of information is presented for each subrogee orlienholder. Typically, the subrogee is the client's insurance companywho has paid the client at least a portion of the amount sought from thedefendant's insurance company. This information includes a radio buttonicon selection to show whether a subrogation or lien is involved andidentifies the subrogee or lienholder accordingly. A data field for theamount of the claim of the subrogee or lienholder and a data field ofthe amount paid are also displayed for each set. Several check box iconsare included in each information set. One of these check box icons isused to confirm whether to write a settlement check to the correspondingsubrogee or leinholder and another of these box icons is used to confirmwhether to include the item in the itemized settlement breakdowndescription. The management program automatically reduces the amountpaid to the subrogee/lienholder by a percentage to the paid to theattorney.

Selection of button icon 804 e displays information relating touninsured motorist (UM) and underinsured motorist (UIM) coverage inwindow 810. Typically, this coverage is provided by the client's owninsurance and operates as a source of compensation for the client. Aninformation set is provided for each policy. Each set includes fields toidentify the insurer and the settlement amount. The set also includes acheck box icon to indicate receipt of the check for the UM/UIMsettlement and another check box icon to indicate the UM/UIM settlementcheck has been deposited.

Button icon 812 is selected to generate a settlement letter which isforwarded with a check for the client's share of the settlementproceeds. This letter includes the itemized settlement breakdown of allcompensation (settlement) sources; and expenses, costs, and fees paid onbehalf of the client. The program automatically calculates the amountpaid to the client from these accounting entries. Button icon 812 willnot permit generation of the letter until all outstanding settlementshave been deposited (defendant, underinsured motorist, and uninsuredmotorist claims) and all amounts owed by the client are ascertained andverified. Button icon 814 is selected to preview checks which may begenerated with the program. Button icon 816 is selected to generatechecks to pay all debts of the client owed from the settlement amountand to provide the client their share of the settlement proceeds.Password access is required to generate settlement checks through theselection of button icon 816. Similar to the generation of a settlementletter, the generation and printing of settlement checks with buttonicon 816 requires that all settlements and amounts owed be finalized andverified. Button icon 816 initiates routines that examine the accountingentries and confirm that all relevant accounting entries from thesettlement, expenses, providers, subrogation, and UIM information setshave been verified. These routines display a summary of unverified itemswhich must be confirmed by the operator before the system will allowsettlement checks to be generated.

Workform 801 provides an efficient technique to calculate and disbursesettlement proceeds with a considerable reduction in the chances oferror compared to conventional methods. It should be understood that theinformation presented in workform 801 is a part of each client recordand may readily be utilized as the workform described in connection withFIG. 2B.

Referring back to FIG. 2, if conditional 124 is not satisfied, thenconditional 126 is encountered which tests whether an AlternativeDispute Resolution (ADR) hearing is set to be held. If an ADR is beingformed, then operation 127 corresponds to the execution of number ofprompts scheduled by setting anchor 5 to the ADR hearing date. Ten daysbefore the anchor 5 date (ADR hearing date), the program prompts anoperator to determine the type of ADR (mediation or arbitration), andmake appropriate entry into the corresponding client record. Next, theoperator is prompted to generate a letter to the client confirmingwhether it is an arbitration or mediation in accordance with dataentered in the client record in response to the type of ADR determined.Also at the ten day point, the program prompts the operator to determinewhether the defendant is represented by insurance or alternatively by anattorney, and then prompts generation of a confirmation letterreflecting the appropriate ADR type to the appropriate representative ofthe defendant. Five days before the anchor 5 date, the program promptsthe operator to check whether a statement has been filed with themediator or arbitrator, and prompts the operator to generate and sendthe statement if not yet filed. Two days before the anchor 5 date, theprogram prompts telephone calls to the client, opposition, andmediator/arbitrator confirming the hearing.

If an ADR hearing has not been set, then conditional 128 is encountered.In conditional 128, a test is performed to determine if litigation hasbeen initiated. If it has, then anchor 6 is set to the date the filedstamped complaint is returned. The scheduling of prompts for anchor 6 isdetailed in scheduling routine 500 of FIG. 6. Routine 500 starts bytiming 30 days from the return of the marked complaint (anchor 6 date)in block 502. At the 30 day point, the program prompts the operator todetermine if an answer to the complaint, notice of service of thecomplaint on the defendant or defendant's representative, or a requestfor an enlargement of time to answer has been received in conditional504. If service of the complaint is not verified, then the operator isprompted to re-serve the complaint in operation 506. If an answer isreceived, then preparation of informal (paper) discovery is prompted inoperation 508.

Next, the program times a total of 60 days from the anchor 6 date inblock 510. The program then re-prompts whether the answer, notice ofservice, or enlargement of time to answer in conditional 512. If serviceis not verified at the 60 day point, then re-service is prompted inoperation 514. If an answer is received, then preparation of informaldiscovery is prompted in operation 516. If discovery has already beenprepared in operation 508, then operation 516 may be ignored. Theprogram then times a total lapse of 90 days from the anchor 6 date inoperation 518 and prompts preparation and filing of a motion to set thetrial date with the court. The program times 180 days from the anchor 6date in operation 520 and executes a conditional to prompt thedetermination of whether a trial date has been set. If the trial datehas not been set, operation 522 is encountered which prompts generationand filing of a second motion to set a trial date with the court. Theprompts of schedule 500 are then completed.

Anchors 7-16 are also provided to facilitate the advancement andtracking for discovery performed by all parties to the lawsuit. Anchor 7is set to the date a first set of informal discovery requests are sentto the defendant. Several prompts are conditionally provided by aprogram at various intervals relative to the anchor 7 date. Theseprompts follow-up on receipt of a response to the discovery sent onbehalf of the client, and results in prompting a motion to be filed withthe court to compel answers to the discovery if a response is notprovided after following-up. Anchors 8 and 9 are directed to trackingsecond and third sets of informal discovery, respectively. Anchors 8 and9 employ the same schedule of conditional prompts as anchor 7.

Anchors 10-12 are directed to various dates related to the arrangementand performance of a deposition on behalf of the client. Anchor 13 isset to the date informal discovery of the client (plaintiff) is receivedfrom the defendant. A series of prompts are scheduled relative to theanchor 13 date to assure a response is generated and sent to thedefendant's representative. Anchors 14 is set to the date the depositionof the client by the defendant has actually been arranged. Anchor 14prompts the generation of confirmation letters to the client and thedefendant's attorney. Anchors 15 and 16 are directed to confirming thedeposition just prior to the arranged date and to assure a copy of thetranscript is received from the court reporter, reviewed by the client,and returned with comments as needed.

Anchor 17 is set to the date a trial for a client's case is set to beheld. Anchor 17 is detailed in scheduling routine 600 of FIGS. 7A and7B. Routine 600 starts by prompting the generation of dispositivemotions 95 days before the trial start date (anchor 17 date) inoperation 602. Block 604 signifies timing by the program to flag thepoint 90 days before the anchor 17 date. At the 90 day point,conditional 606 inquires into whether dispositive motions have beenmailed. If not, mailing of the motions is prompted under operation 608.The program times 65 days prior to trial and prompts preparation of apreliminary witness and exhibit list for filing with the court underoperation 610. Operation 610 also prompts filing of a list ofcontentions concerning the client's case which outline the client'sposition with respect to pertinent factual and legal issues. Operation610 also prompts preparation and filing of motions in limine.

At 60 days before trial, as represented by block 612, conditional 614prompts the determination of whether motions in limine have been filed.If motions in limine have not been filed, then mailing of the motions isprompted in operation 616. Next, operation 618 is encountered whereincompletion of formal discovery is prompted. In addition, operation 618prompts preparation and delivery of an affidavit to one or more medicalproviders to be executed and returned for presentation as evidenceduring trial. In block 620, time lapses until 35 days before trial whenconditional 622 prompts to determine whether all outside informationneeded for trial has been received. If information is missing,completion of discovery is prompted in operation 624. At the 35 daypoint, operation 626 prompts the preparation of final witness andexhibit lists. After waiting until 30 days before trial, as representedby operation 628, conditional 630 prompts to determine whether the finalwitness and exhibit lists have been mailed. If the final lists have notbeen mailed, mailing of the final lists is prompted by operation 632. At30 days before trial, the program also prompts the preparation andfiling of proposed jury instructions under operation 634.

At 20 days before trial, the program prompts contacting the witness byletter under operation 636. Also, operation 636 prompts contactingmedical providers by telephone from which affidavits have not beenreceived. At 15 days before trial, as represented by block 638,conditional 640 tests whether any affidavits to medical providers stillneed to be mailed. If one or more affidavits do need to be mailed, thenoperation 642 prompts this mailing.

At 5 days before trial, the preparation of subpoenas and letters towitnesses is prompted. Also, conditional 646 prompts the determinationof whether jury questionnaires have been received 5 days before theanchor 17 date. If not, operation 648 prompts contacting the clerk ofthe court to obtain the questionnaires. Routine 600 is then completed.

Collectively, each of anchors 1-18 initiates a sequence of conditionalprompts which are scheduled to advance the client's case. In oneembodiment, anchor 1 is initiated concurrently with anchor 2 uponcreation of a new client record. Anchor 3 is initiated and clears anchor2 once medical treatment is complete, removing any outstanding promptsof anchor 2. Similarly, sending a demand letter and correspondinglysetting anchor 4 clears anchor 3 in this embodiment. On the other hand,Anchors 6-17 are permitted to operate concurrently given the nature ofthe litigation process.

Also, various other prompt schedules may be generated either separatefrom or in addition to various anchors. Generally, these independentschedules represent the operation of automated ticklers that areexecuted and tracked for a given client record by the management programindependent of anchor dates or case phase. Furthermore, theseindependent prompts schedules may be set as often as needed for the sameclient and for multiple client records independent of one another. FIGS.8A-8E illustrate several of the independent prompt schedules provided bythe management program embodied in the computer program listing of theMicrofiche Appendix.

FIG. 8A is a flow diagram of schedule 710. Schedule 710 is initiated bystarting a corresponding automated tickler with the ADR hearing date.Schedule 710 may be selected as an alternative to the anchor 5 scheduleor otherwise employed throughout management of a client's case. Schedule710 begins with block 712 which represents 10 days before theestablished ADR hearing date. At the 10 day point, conditional 714determines whether the ADR is arbitration or mediation. If it isarbitration, operation 716 prompts preparation and delivery of anarbitration letter to the client. Otherwise, operation 718 promptsgeneration and delivery of a mediation letter to the client. Conditional720 tests whether the defendant is represented by insurance or apersonal attorney. If the defendant is represented by insurance, an ADRconfirmation letter is prompted to the insurance attorney in operation722. Otherwise, a letter to the defendant's personal attorney isprompted in operation 724.

Block 726 is next encountered which represents timing of 5 days beforethe ADR date. At this 5 day point, conditional 728 prompts whether anADR statement has been filed with the mediator or arbitrator asappropriate. If the statement has not been filed, operation 730 promptspreparation and filing of the statement. In operation 732, the programprompts the attorney to place confirmation telephone calls to theappropriate parties. Schedule 710 is then completed.

FIG. 8B is a flow diagram of prompt schedule 740 which may be set foreach deposition of the client by the defendant. Schedule 740 isinitiated by starting a corresponding automated tickler with thedeposition date. Schedule 740 is configured to be set multiple times foreach client. This schedule may be used in lieu of, or in addition toanchors 14-16 associated with the stage 130 of the litigation phase.Schedule 740 starts in operation 741 by prompting confirmation calls tothe client and opposing counsel 5 days before the deposition date.Control flows from operation 741 to conditional 742 to test whether atranscript for the deposition has been received 15 days after thedeposition was taken. If the transcript was not received, operation 743prompts generation of a letter to the reporter for the depositiontranscript. Otherwise, the operator is prompted to forward thetranscript to the client for review under operation 744. This reviewgives the client an opportunity to point out any inaccuracies or provideother comments as required. Next, conditional 746 is encountered whichprompts whether the transcript has been received within 30 daysfollowing the deposition. If not, operation 747 prompts generation of aletter to the reporter requesting the transcript. Otherwise, theoperator is prompted to forward a transcript copy to the client forreview under operation 748 if the client has not yet received thetranscript under operation 744. At 45 days after the deposition,conditional 749 tests whether the client has returned the transcript. Ifthe copy has not been returned by the client, a telephone call to theclient is prompted in operation 750. Otherwise, the transcript isforwarded to the court reporter in operation 751.

FIG. 8C is a flow diagram of prompt schedule 760 which is directed totracking and responding to informal discovery served on the client bythe defendant which may be in addition to or in lieu of anchor 13.Schedule 760 is initiated by setting a corresponding automated ticklerto the date the defendant's informal discovery is received. Schedule 760starts with operation 761 which prompts the preparation and filing of amotion for an enlargement of time to respond to the discovery.

Also, operation 761 prompts delivery of a copy of the discoverydocuments to the client. Block 762 represents the passage of 30 daysform the date the discovery is received. At this 30 day point,conditional 763 is prompted which tests whether the discovery responsehas been sent. If the response has not been sent, then operation 764prompts generation and filing of a second motion to enlarge the time torespond.

Block 765 is next encounter which times a total of 60 days from theservice of the discovery. Conditional 766 prompts inquiry into whetherthe response has been sent at this 60 day point. If not, then operation767 prompts a telephone call to the client. Schedule 760 is thenregarded as complete.

FIG. 8D is a flow diagram of prompt schedule 770 which is directed totracking a deposition conducted by the plaintiff. Schedule 770 isinitiated by setting a corresponding automated tickler to the depositiondate. Schedule 770 may be used in addition to or in lieu of anchors10-12. The program prompts confirmation calls to the client and opposingcounsel 5 days before the scheduled deposition under operation 771.Block 772 times 40 days after the deposition date. At the 40 day point,conditional 773 prompts the determination of whether the depositiontranscript has been received. If the transcript has not been received,then the transcript is requested from the reporter in operation 774.Next block 775 is encountered which times 70 days after the deposition.At the 70 day point, conditional 776 tests whether the transcript hasyet been received. If the transcript has not been received, thenoperation 777 prompts a second request for original transcript from thereporter. At this point, schedule 770 is complete.

FIG. 8E is a flow diagram of prompt schedule 780 which is directed totracking progress of informal (paper) discovery served by the client(plaintiff) on others. Schedule 780 may be set one or more times for agiven client to track informal discovery either in addition to or inlieu of anchors 7-9. Schedule 780 is initiated by setting acorresponding automated tickler to the date the discovery is served.Schedule 780 starts by timing 40 days from the date discovery is servedand then executes conditional 781 to prompt an inquiry into whether aresponse was received from the recipient of the discovery. If theresponse has not been received, a request letter is sent to opposingcounsel in operation 782. Otherwise, depositions on behalf of the clientare set-up in operation 783. The deposition set-up may be accomplishedby setting anchors 10-12 or initiating schedule 740 one or more times asrequired. Next, block 784 represents a time lapse of 70 days from thediscovery service date. Conditional 785 is next encountered which againtests whether a discovery response has been received. If not, then asecond discovery letter is prompted in operation 786. Otherwisedepositions are initiated in operation 783. Block 788 then times a totallapse of 100 days. At the 100 day point, conditional 789 is encounteredwhich tests again for a response. If a discovery response has still notbeen received, the operator is prompted to prepare and file a motion tocompel discovery with the court under operation 790. Otherwise,depositions are arranged in operation 783 if not already done so.Schedule 780 is then complete.

In another feature of the present invention, follow-up prompts forvarious request letters generated by the management program may begenerated by implementing automated ticklers in lieu of or in additionto prompts and ticklers of the various anchor schedules. In oneembodiment, requests for medical records are generated with themanagement program during the pendency of anchor 2 for those medicalproviders whose treatment is already completed. When these requests aresent on behalf of clients, automated ticklers are set to automaticallyprompt a follow-up request letter or phone call after the passage of apredetermined amount of time. Notably, the medical record requestoperators of routine 200 for anchor 3 may still be used to request therecords of the medical provider who treated the client up to the releaseof the client from medical treatment. Indeed, numerous automatedticklers of this type may be simultaneously set as needed for eachclient record independent of the anchor prompts.

As used herein, it should be appreciated that: “record,” “form,”“operation,” “icon,” “variable,” “value,” “buffer,” “constant,” “flag,”“memory space,” or “memory location” each generally correspond to a“signal” within processor 30 of the present invention. Furthermore itshould be appreciated that as used herein: “variable,” “value,”“buffer,” “constant,” “flag,” “threshold,” “input,” “output,” “pixel,”“image” (or a region thereof), “matrix,” “command,” or “memory location”each generally correspond to one or more signals within processingequipment of the present invention.

It is contemplated that various operations, records, icons, stages,conditionals, procedures, thresholds, blocks, forms, schedules,routines, and processes described in connection with the presentinvention could be altered, rearranged, substituted, deleted,duplicated, combined, or added to other processes as would occur tothose skilled in the art without departing from the spirit of thepresent invention.

All publications, patents, and patent applications cited in thisspecification are herein incorporated by reference as if each individualpublication, patent, or patent application were specifically andindividually indicated to be incorporated by.

While the invention has been illustrated and described in detail in thedrawings and foregoing description, the same is to be considered asillustrative and not restrictive in character, it being understood thatonly the preferred embodiment has been shown and described and that allchanges and modifications that come within the spirit of the inventionare desired to be protected.

1-48. (canceled)
 49. A method, comprising: executing a program with acomputer to establish a number of client records corresponding to aplurality of personal injury claims, the records each including anindication of claim status; automatically scheduling a computer promptto an operator with the program in response to generating a request forinformation relative to one of the claims; providing the prompt to theoperator after a period of time passes; receiving the information inresponse to the prompt; entering data into one of the recordscorresponding to the information; setting the indication for the one ofthe records to represent a pre-negotiation phase of the one of theclaims; sending one or more other requests for further information fromone or more other parties in response to one or more correspondingoperator prompts generated by the program during the pre-negotiationphase; providing a communication to demand compensation for the personalinjury after the further information is received and entered into theone of the records; and changing the indication for the one of therecords to represent a negotiation phase of the one of the claims. 50.The method of claim 49, wherein the further information include medicaltreatment data and the one or more other parties include a medicaltreatment provider.
 51. The method of claim 49, wherein the computerprompt is one of a sequence of prompts automatically scheduled by theprogram in response to generation of the request.
 53. The method ofclaim 49, further comprising switching the indication to a litigationphase after said changing.
 54. The method of claim 49, furthercomprising switching the indication to a settlement phase after saidchanging.
 55. The method of claim 49, wherein the pre-negotiation phaseincludes a first subordinate stage and a second subordinate stage, theprogram generating a first set of ticklers during the first subordinatestage and a second set of ticklers during the second subordinate stage,the one or more operator prompts belonging to the second set ofticklers.
 56. A method, comprising: executing a program with a computerto manage a number of personal injury claims represented by a number ofclient records; automatically scheduling a computer prompt to anoperator with the program in response to generating a request forinformation relative to one of the claims; providing the prompt to theoperator after a period of time passes; receiving the information inresponse to the prompt; entering data into the one of the recordscorresponding to the information; prompting generation of anotherrequest to obtain data relative to another of the claims; automaticallyscheduling a follow up prompt with the program in response to saidprompting; and receiving the data in response to the follow up promptfor entry into another of the records.
 57. The method of claim 56,wherein the data includes medical treatment information.
 58. The methodof claim 56, wherein the computer prompt is one of a sequence of promptsautomatically scheduled by the program in response to generation of therequest.
 59. The method of claim 56, which includes: providing a claimstatus indication of the one of the records; and changing the indicationfrom a pre-negotiation phase to a negotiation phase after enteringmedical treatment data into the one of the records.
 60. The method ofclaim 59, further comprising switching the indication to a settlementphase after said changing.
 61. The method of claim 59, wherein thepre-negotiation phase includes a first subordinate stage and a secondsubordinate stage, the program generating a first set of ticklers duringthe first subordinate stage and a second set of ticklers during thesecond subordinate stage.
 62. An apparatus, comprising: a computeroperable to execute a program to establish a number of client recordscorresponding to a plurality of personal injury claims, the records eachincluding an indication of claim status, the program being operable to:automatically schedule a computer prompt to an operator in response togeneration of a request for information relative to one of the claims;provide the prompt to the operator after a period of time passes;receive the information in one of the records in response to the prompt;set the indication for the one of the records to represent apre-negotiation phase of the first one of the claims; prompt one or moreother requests for further information from one or more other partiesduring the pre-negotiation phase; provide a communication to demandcompensation for the personal injury after the further information isentered into the one of the records; and changing the indication for theone of the records to represent a negotiation phase for the one of theclaims.